PR Summary

• Migration from Deployment to StatefulSet in deployment.yaml
  The type of resource has now been changed from Deployment to StatefulSet. This update enhances the management of the stateful nature of our application, providing stable, unique network identifiers, stable persistent storage, and orderly deployment and scaling.

• Deployment Name Updated
  The deployment name has been updated to 'reactibot' from 'reactibot-deployment', increasing simplicity and clarity.

• Introduction of ServiceName
  The field 'serviceName' with the value 'reactibot-service' has been added. This change connects the StatefulSet to the specified service, allowing our network to function efficiently.

• Addition of VolumeClaimTemplates
  New volumeClaimTemplates have been added, creating a persistent volume claim for 'reactibot-data' with 1Gi of storage. This change ensures the application data persists across restarts, thus improving our data reliability and availability.

• Volume Mounts in Container Spec
  The volume named 'reactibot-data' will now be mounted at /data in the container. This allows the application to access the important data stored in this volume.

• Update to variable-config.yaml
  Reflecting the change from Deployment to StatefulSet, updates to variable-config.yaml have been made. This makes sure that our configuration aligns with the new implementation.

• Creation of volume.yaml
  A new file named volume.yaml has been created, defining a PersistentVolume named 'reactibot-pv' with 1Gi storage. This setting provides physical storage to our claim in the same way traditional storage devices do in a non-cloud environment. It provides a beneficial abstraction of the underlying storage making it easier to manage and ensures our data durability.